-
Notifications
You must be signed in to change notification settings - Fork 29
Website Redesign #204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Website Redesign #204
Conversation
- added element with text and image split - responsive adaptations to connected components - simplified paddings in containers
- added donation button section - added links to QVLab button
- Added data files for lectures and university courses - Reduced html, improved readbility of remaining html - Restructered layout and css to allow for more markdown
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Langhaarzombie! I did a first pass review.
What else is left on your list for before merging this?
index.html
Outdated
<a href="https://www.jst.go.jp/kisoken/presto/en/"><img src="images/presto.jpg"></a> | ||
<div class="col-md-6"> | ||
<center><h4>Distribution of the 39,420 Unique Visitors in 2020</h4></center> | ||
<div id='container1' style='margin-top:10px; position: relative;height: 250px;'></div> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should either remove or update this as part of the website revamp. Not for this PR necessarily.
Co-authored-by: Simon Cross <[email protected]>
Thanks a lot!
There are a couple things left:
|
This PR is to track the technical changes that are part of the website redesign. Since the Git Hub pages in QuTiP are spread around multiple repos, this PR will be referenced so to keep track of things.
For now, it is based on the master branch. We should however consider creating a
dev
branch to keep potential changes from affecting the live website.